Autonomous bandwidth part switching

ABSTRACT

Apparatuses, methods, and systems are disclosed for autonomous bandwidth part switching. One method includes determining that a channel parameter corresponding to an active uplink bandwidth part of a serving cell is greater than a predetermined value at a time in which the active uplink bandwidth part is a first bandwidth part. The method includes, in response to determining that the channel parameter is greater than the predetermined value, autonomously switching the active uplink bandwidth part from the first uplink bandwidth part to a second uplink bandwidth part configured for the serving cell, wherein switching the active uplink bandwidth part comprises deactivating the first uplink bandwidth part.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. patent application Ser. No.16/741,427 filed on Jan. 13, 2020, which claims priority to U.S. PatentApplication Ser. No. 62/795,872 entitled “TEMPORARY DEACTIVATION OF ANAUTONOMOUS UPLINK OF AN NR-U CELL” and filed on Jan. 23, 2019 forJoachim Loehr, all of which are incorporated herein by reference intheir entirety.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to autonomous bandwidthpart switching.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), 5^(th) Generation (“5G”), 5G QoS Indicator(“5QI”), Positive-Acknowledgment (“ACK”), Aggregation Level (“AL”),Access and Mobility Management Function (“AMF”), Access Point (“AP”),Access Stratum (“AS”), Autonomous Uplink (“AUL”), Beam Failure Detection(“BFD”), Beam Failure Recovery (“BFR”), Binary Phase Shift Keying(“BPSK”), Base Station (“BS”), Buffer Status Report (“BSR”), Bandwidth(“BW”), Bandwidth Part (“BWP”), Cell RNTI (“C-RNTI”), CarrierAggregation (“CA”), Contention-Based Random Access (“CBRA”), ClearChannel Assessment (“CCA”), Common Control Channel (“CCCH”), ControlChannel Element (“CCE”), Cyclic Delay Diversity (“CDD”), Code DivisionMultiple Access (“CDMA”), Control Element (“CE”), Contention-Free RandomAccess (“CFRA”), Closed-Loop (“CL”), Coordinated Multipoint (“CoMP”),Channel Occupancy Time (“COT”), Cyclic Prefix (“CP”), CyclicalRedundancy Check (“CRC”), Channel State Information (“CSI”), ChannelState Information-Reference Signal (“CSI-RS”), Common Search Space(“CSS”), Control Resource Set (“CORESET”), Downlink Feedback Information(“DFI”), Discrete Fourier Transform Spread (“DFTS”), Downlink ControlInformation (“DCI”), Downlink (“DL”), Demodulation Reference Signal(“DMRS”), Data Radio Bearer (“DRB”), Discontinuous Reception (“DRX”),Downlink Pilot Time Slot (“DwPTS”), Enhanced Clear Channel Assessment(“eCCA”), Enhanced LAA (“eLAA”), Enhanced Mobile Broadband (“eMBB”),Evolved Node B (“eNB”), Effective Isotropic Radiated Power (“EIRP”),European Telecommunications Standards Institute (“ETSI”), Frame BasedEquipment (“FBE”), Frequency Division Duplex (“FDD”), Frequency DivisionMultiplexing (“FDM”), Frequency Division Multiple Access (“FDMA”),Frequency Division Orthogonal Cover Code (“FD-OCC”), Frequency Range1—sub 6 GHz frequency bands and/or 410 MHz to 7125 MHz (“FR1”),Frequency Range 2-24.25 GHz to 52.6 GHz (“FR2”), 5G Node B or NextGeneration Node B (“gNB”), Global Navigation Satellite System (“GNSS”),General Packet Radio Services (“GPRS”), Guard Period (“GP”), GlobalPositioning System (“GPS”), Global System for Mobile Communications(“GSM”), Globally Unique Temporary UE Identifier (“GUTI”), Home AMF(“hAMF”), Hybrid Automatic Repeat Request (“HARQ”), Home LocationRegister (“HLR”), Handover (“HO”), Home PLMN (“HPLMN”), Home SubscriberServer (“HSS”), Identity or Identifier (“ID”), Information Element(“IE”), International Mobile Equipment Identity (“IMEI”), InternationalMobile Subscriber Identity (“IMSI”), International MobileTelecommunications (“IMT”), Internet-of-Things (“IoT”), Layer 1 (“L1”),Layer 2 (“L2”), Layer 3 (“L3”), Licensed Assisted Access (“LAA”), LoadBased Equipment (“LBE”), Listen-Before-Talk (“LBT”), Logical Channel(“LCH”), Logical Channel Prioritization (“LCP”), Log-Likelihood Ratio(“LLR”), Long Term Evolution (“LTE”), Multiple Access (“MA”), MediumAccess Control (“MAC”), Multimedia Broadcast Multicast Services(“MBMS”), Modulation Coding Scheme (“MCS”), Master Information Block(“MIB”), Multiple Input Multiple Output (“MIMO”), Mobility Management(“MM”), Mobility Management Entity (“MME”), Mobile Network Operator(“MNO”), massive MTC (“mMTC”), Maximum Power Reduction (“MPR”), MachineType Communication (“MTC”), Multi User Shared Access (“MUSA”), NonAccess Stratum (“NAS”), Narrowband (“NB”), Negative-Acknowledgment(“NACK”) or (“NAK”), New Data Indicator (“NDI”), Network Entity (“NE”),Network Function (“NF”), Non-Orthogonal Multiple Access (“NOMA”), NewRadio (“NR”), NR Unlicensed (“NR-U”), Network Repository Function(“NRF”), Network Slice Instance (“NSI”), Network Slice SelectionAssistance Information (“NSSAI”), Network Slice Selection Function(“NSSF”), Network Slice Selection Policy (“NSSP”), Operation andMaintenance System (“OAM”), Orthogonal Frequency Division Multiplexing(“OFDM”), Open-Loop (“OL”), Other System Information (“OSI”), PowerAngular Spectrum (“PAS”), Physical Broadcast Channel (“PBCH”), PowerControl (“PC”), UE to UE interface (“PC5”), Primary Cell (“PCell”),Policy Control Function (“PCF”), Physical Cell Identity (“PCI”),Physical Downlink Control Channel (“PDCCH”), Packet Data ConvergenceProtocol (“PDCP”), Packet Data Network Gateway (“PGW”), PhysicalDownlink Shared Channel (“PDSCH”), Pattern Division Multiple Access(“PDMA”), Packet Data Unit (“PDU”), Physical Hybrid ARQ IndicatorChannel (“PHICH”), Power Headroom (“PH”), Power Headroom Report (“PHR”),Physical Layer (“PHY”), Public Land Mobile Network (“PLMN”), PhysicalRandom Access Channel (“PRACH”), Physical Resource Block (“PRB”),Physical Sidelink Control Channel (“PSCCH”), Primary Secondary Cell(“PSCell”), Physical Uplink Control Channel (“PUCCH”), Physical UplinkShared Channel (“PUSCH”), Quasi Co-Located (“QCL”), Quality of Service(“QoS”), Quadrature Phase Shift Keying (“QPSK”), Registration Area(“RA”), RA RNTI (“RA-RNTI”), Radio Access Network (“RAN”), Radio AccessTechnology (“RAT”), Random Access Procedure (“RACK”), Random AccessPreamble Identifier (“RAPID”), Random Access Response (“RAR”), ResourceBlock Assignment (“RBA”), Resource Element Group (“REG”), Radio LinkControl (“RLC”), RLC Acknowledged Mode (“RLC-AM”), RLC UnacknowledgedMode/Transparent Mode (“RLC-UM/TM”), Radio Link Monitoring (“RLM”),Radio Network Temporary Identifier (“RNTI”), Reference Signal (“RS”),Remaining Minimum System Information (“RMSI”), Radio Resource Control(“RRC”), Radio Resource Management (“RRM”), Resource Spread MultipleAccess (“RSMA”), Reference Signal Received Power (“RSRP”), Round TripTime (“RTT”), Receive (“RX”), Sparse Code Multiple Access (“SCMA”),Scheduling Request (“SR”), Sounding Reference Signal (“SRS”), SingleCarrier Frequency Division Multiple Access (“SC-FDMA”), Secondary Cell(“SCell”), Secondary Cell Group (“SCG”), Shared Channel (“SCH”),Sub-carrier Spacing (“SCS”), Service Data Unit (“SDU”), Serving Gateway(“SGW”), System Information Block (“SIB”), SystemInformationBlockType1(“SIB1”), SystemInformationBlockType2 (“SIB2”), SubscriberIdentity/Identification Module (“SIM”),Signal-to-Interference-Plus-Noise Ratio (“SINR”), Sidelink (“SL”),Service Level Agreement (“SLA”), Sidelink Synchronization Signals(“SLSS”), Session Management Function (“SMF”), Special Cell (“SpCell”),Single Network Slice Selection Assistance Information (“S-NSSAI”),Scheduling Request (“SR”), Signaling Radio Bearer (“SRB”), Shortened TTI(“sTTI”), Synchronization Signal (“SS”), Sidelink SSB (“S-SSB”),Synchronization Signal Block (“SSB”), Supplementary Uplink (“SUL”),Subscriber Permanent Identifier (“SUPI”), Timing Advance (“TA”), TimingAlignment Timer (“TAT”), Transport Block (“TB”), Transport Block Size(“TBS”), Time-Division Duplex (“TDD”), Time Division Multiplex (“TDM”),Time Division Orthogonal Cover Code (“TD-OCC”), Transmission PowerControl (“TPC”), Transmission Reception Point (“TRP”), Transmission TimeInterval (“TTI”), Transmit (“TX”), Uplink Control Information (“UCI”),Unified Data Management Function (“UDM”), Unified Data Repository(“UDR”), User Entity/Equipment (Mobile Terminal) (“UE”), Uplink (“UL”),UL SCH (“UL-SCH”), Universal Mobile Telecommunications System (“UMTS”),User Plane (“UP”), UP Function (“UPF”), Uplink Pilot Time Slot(“UpPTS”), Ultra-reliability and Low-latency Communications (“URLLC”),UE Route Selection Policy (“URSP”), Vehicle-to-Vehicle (“V2V”), VisitingAMF (“vAMF”), Visiting NSSF (“vNSSF”), Visiting PLMN (“VPLMN”), andWorldwide Interoperability for Microwave Access (“WiMAX”).

In certain wireless communications networks, it may be undesirable tocontinue to use an active bandwidth part.

BRIEF SUMMARY

Methods for autonomous bandwidth part switching are disclosed.Apparatuses and systems also perform the functions of the methods. Oneembodiment of a method includes determining that a channel parametercorresponding to an active uplink bandwidth part of a serving cell isgreater than a predetermined value at a time in which the active uplinkbandwidth part is a first bandwidth part. In some embodiments, themethod includes, in response to determining that the channel parameteris greater than the predetermined value, autonomously switching theactive uplink bandwidth part from the first uplink bandwidth part to asecond uplink bandwidth part configured for the serving cell, whereinswitching the active uplink bandwidth part comprises deactivating thefirst uplink bandwidth part.

One apparatus for autonomous bandwidth part switching includes aprocessor that: determines that a channel parameter corresponding to anactive uplink bandwidth part of a serving cell is greater than apredetermined value at a time in which the active uplink bandwidth partis a first bandwidth part; and in response to determining that thechannel parameter is greater than the predetermined value, autonomouslyswitches the active uplink bandwidth part from the first uplinkbandwidth part to a second uplink bandwidth part configured for theserving cell, wherein switching the active uplink bandwidth partcomprises deactivating the first uplink bandwidth part.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for autonomous bandwidth part switching;

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for autonomous bandwidth part switching;

FIG. 3 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for transmitting information; and

FIG. 4 is a flow chart diagram illustrating one embodiment of a methodfor autonomous bandwidth part switching.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer readable storage devices storing machine readable code,computer readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Certain of the functional units described in this specification may belabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom very-large-scale integration(“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such aslogic chips, transistors, or other discrete components. A module mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, include one or more physical or logical blocks of executablecode which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together, but may include disparate instructionsstored in different locations which, when joined logically together,include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different computer readable storage devices.Where a module or portions of a module are implemented in software, thesoftware portions are stored on one or more computer readable storagedevices.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. The code may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

FIG. 1 depicts an embodiment of a wireless communication system 100 forautonomous bandwidth part switching. In one embodiment, the wirelesscommunication system 100 includes remote units 102 and network units104. Even though a specific number of remote units 102 and network units104 are depicted in FIG. 1 , one of skill in the art will recognize thatany number of remote units 102 and network units 104 may be included inthe wireless communication system 100.

In one embodiment, the remote units 102 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), aerialvehicles, drones, or the like. In some embodiments, the remote units 102include wearable devices, such as smart watches, fitness bands, opticalhead-mounted displays, or the like. Moreover, the remote units 102 maybe referred to as subscriber units, mobiles, mobile stations, users,terminals, mobile terminals, fixed terminals, subscriber stations, UE,user terminals, a device, or by other terminology used in the art. Theremote units 102 may communicate directly with one or more of thenetwork units 104 via UL communication signals. In certain embodiments,the remote units 102 may communicate directly with other remote units102 via sidelink communication.

The network units 104 may be distributed over a geographic region. Incertain embodiments, a network unit 104 may also be referred to as anaccess point, an access terminal, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, a device, a core network, anaerial server, a radio access node, an AP, NR, a network entity, an AMF,a UDM, a UDR, a UDM/UDR, a PCF, a RAN, an NSSF, or by any otherterminology used in the art. The network units 104 are generally part ofa radio access network that includes one or more controllerscommunicably coupled to one or more corresponding network units 104. Theradio access network is generally communicably coupled to one or morecore networks, which may be coupled to other networks, like the Internetand public switched telephone networks, among other networks. These andother elements of radio access and core networks are not illustrated butare well known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system 100 iscompliant with NR protocols standardized in 3GPP, wherein the networkunit 104 transmits using an OFDM modulation scheme on the DL and theremote units 102 transmit on the UL using a SC-FDMA scheme or an OFDMscheme. More generally, however, the wireless communication system 100may implement some other open or proprietary communication protocol, forexample, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants,CDMA2000, Bluetooth®, ZigBee, Sigfoxx, among other protocols. Thepresent disclosure is not intended to be limited to the implementationof any particular wireless communication system architecture orprotocol.

The network units 104 may serve a number of remote units 102 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The network units 104 transmit DL communicationsignals to serve the remote units 102 in the time, frequency, and/orspatial domain.

In one embodiment, a remote unit 102 may determine that a channelparameter corresponding to an active uplink bandwidth part of a servingcell is greater than a predetermined value at a time in which the activeuplink bandwidth part is a first bandwidth part. In some embodiments,the remote unit 102 may, in response to determining that the channelparameter is greater than the predetermined value, autonomously switchthe active uplink bandwidth part from the first uplink bandwidth part toa second uplink bandwidth part configured for the serving cell, whereinswitching the active uplink bandwidth part comprises deactivating thefirst uplink bandwidth part. Accordingly, the remote unit 102 may beused for autonomous bandwidth part switching.

FIG. 2 depicts one embodiment of an apparatus 200 that may be used forautonomous bandwidth part switching. The apparatus 200 includes oneembodiment of the remote unit 102. Furthermore, the remote unit 102 mayinclude a processor 202, a memory 204, an input device 206, a display208, a transmitter 210, and a receiver 212. In some embodiments, theinput device 206 and the display 208 are combined into a single device,such as a touchscreen. In certain embodiments, the remote unit 102 maynot include any input device 206 and/or display 208. In variousembodiments, the remote unit 102 may include one or more of theprocessor 202, the memory 204, the transmitter 210, and the receiver212, and may not include the input device 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 202 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 202 executes instructions stored in thememory 204 to perform the methods and routines described herein. Invarious embodiments, the processor 202 may: determine that a channelparameter corresponding to an active uplink bandwidth part of a servingcell is greater than a predetermined value at a time in which the activeuplink bandwidth part is a first bandwidth part; and, in response todetermining that the channel parameter is greater than the predeterminedvalue, autonomously switch the active uplink bandwidth part from thefirst uplink bandwidth part to a second uplink bandwidth part configuredfor the serving cell, wherein switching the active uplink bandwidth partcomprises deactivating the first uplink bandwidth part. The processor202 is communicatively coupled to the memory 204, the input device 206,the display 208, the transmitter 210, and the receiver 212.

The memory 204, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 204 includes volatile computerstorage media. For example, the memory 204 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 204 includes non-volatilecomputer storage media. For example, the memory 204 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 204 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 204 also stores program code and related data, such as anoperating system or other controller algorithms operating on the remoteunit 102.

The input device 206, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 206 maybe integrated with the display 208, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device206 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 206 includes two ormore different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronicallycontrollable display or display device. The display 208 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 208 includes an electronic display capable of outputtingvisual data to a user. For example, the display 208 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display208 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 208 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakersfor producing sound. For example, the display 208 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 208 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 208 may be integrated with the input device206. For example, the input device 206 and display 208 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 208 may be located near the input device 206.

The transmitter 210 is used to provide UL communication signals to thenetwork unit 104 and the receiver 212 is used to receive DLcommunication signals from the network unit 104, as described herein.

Although only one transmitter 210 and one receiver 212 are illustrated,the remote unit 102 may have any suitable number of transmitters 210 andreceivers 212. The transmitter 210 and the receiver 212 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 210 and the receiver 212 may be part of a transceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used fortransmitting information. The apparatus 300 includes one embodiment ofthe network unit 104. Furthermore, the network unit 104 may include aprocessor 302, a memory 304, an input device 306, a display 308, atransmitter 310, and a receiver 312. As may be appreciated, theprocessor 302, the memory 304, the input device 306, the display 308,the transmitter 310, and the receiver 312 may be substantially similarto the processor 202, the memory 204, the input device 206, the display208, the transmitter 210, and the receiver 212 of the remote unit 102,respectively.

In various embodiments, the transmitter 310 may transmit information.Although only one transmitter 310 and one receiver 312 are illustrated,the network unit 104 may have any suitable number of transmitters 310and receivers 312. The transmitter 310 and the receiver 312 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 310 and the receiver 312 may be part of a transceiver.

In certain configurations, such as for LTE eLAA, AUL transmissions maybe enabled through a combination of RRC signaling and an activationmessage conveyed by DCI in a physical control channel. In variousembodiments, an RRC configuration may include subframes in which a UE isallowed and/or enabled to transmit autonomously, and eligible HARQprocess IDs. In some embodiments, an activation message may include aRBA and a MCS from which a UE may be able to determine a transport blocksize for any AUL transmission.

In various embodiments, it may be possible to autonomously retransmitdata pertaining to a transport block that has not been receivedcorrectly by an eNB. In such embodiments, a UE may monitor DFI that maybe transmitted by the eNB and may include HARQ-ACK information forAUL-enabled HARQ process IDs. In some embodiments, if a UE detects aNACK message, the UE may try to autonomously access a channel for aretransmission of the same transport block in a corresponding HARQprocess. In certain embodiments, as a safe-guard against errors, anautonomous uplink transmission may include at least a HARQ process IDand an NDI accompanying a PUSCH (e.g., AUL-UCI).

In some embodiments, an eNB may transmit an uplink grant through a DCIthat assigns uplink resources for a retransmission of the same transportblock using a HARQ process. In various embodiments, an eNB transmits anuplink grant through a DCI that assigns uplink resources for atransmission of a new transport block using a HARQ process. In suchembodiments, even though a HARQ process ID may be eligible for AULtransmissions, the eNB may still have access to this process at any timethrough a scheduling grant (e.g., DCI). In certain embodiments, if a UEdetects a grant for an UL transmission for a subframe that is eligiblefor AUL (e.g., according to the RRC configuration), the UL transmissionmay follow the received grant and an AUL transmission may not beperformed in that subframe.

In certain embodiments, unlicensed cells experiencing systematic LBTfailures (e.g., high congestion) may have some negative impact on L2procedures (e.g., LCP procedure, UL transmission procedure, PDCP routingfor split bearer operation). In such embodiments, TBs may be generatedfor transmission on an unlicensed cell and/or PDCP data packets may berouted to unlicensed cells even though actual transmission on PHY maynot occur due to a high number of LBT failures. This may negativelyimpact reordering delays and may be avoided.

As used herein, the term eNB and/or gNB may be used for a base stationbut may be replaceable by any other radio access node (e.g., BS, eNB,gNB, AP, NR, etc.). Moreover, various embodiments described herein maybe described in the context of 5G NR; however, such embodiments may beequally applicable to other mobile communication systems supportingserving cells and/or carriers configured in an unlicensed spectrum LTEmobile wireless or cellular telecommunications system.

In a first embodiment, a UE may autonomously deactivate an uplink of aNR-U cell for a certain time period if the cell is experiencing a highLBT failure rate, a high CCA failure rate, and/or a high channeloccupancy. LBT and/or CCA failure rate measurements (e.g., channeloccupancy measurement) described herein may be performed by the UE whilethe UE has data it intends to transmit as well as if there is nointended transmission by the UE. In such an embodiment, the UE may stillmonitor a downlink of the unlicensed cell for downlink channels such asPDCCH and/or PDSCH. In one embodiment, deactivating an uplink may meanthat a UE may not attempt to or perform any UL transmissions on anunlicensed cell (e.g., no PUCCH transmission, no PUSCH transmission, noSRS transmission, etc.). In one implementation of the first embodiment,the UE may still be allowed to attempt and perform a random accessprocedure (e.g., PRACH transmission) on the NR-U cell that istemporarily deactivated for uplink transmissions. A random accessprocedure may be triggered if the UE autonomously deactivates the uplinkon an NR-U cell experiencing a high LBT failure rate. A predefinedpreamble or PRACH resource may be used to inform the gNB about the highLBT failure rate and that the UE subsequently stopped and/or deactivatedthe uplink.

In another implementation of the first embodiment, the UE mayautonomously deactivate a current uplink BWP of an NR-U cell for acertain time period if the cell is experiencing a high LBT failure rate,a high CCA failure rate, and/or a high channel occupancy. In such animplementation, the UE may switch to the initial BWP or switch toanother BWP (e.g., configured UL BWP).

In certain implementations of the first embodiment, the UE maydeactivate the unlicensed cell that is experiencing a high LBT failurerate, a high CCA failure rate, and/or a high channel occupancy (e.g.,uplink and downlink of the cell—if configured). In such animplementation, the UE is still able to communicate with the networknode (e.g., gNB) over some other aggregated serving cell (e.g., the UEis configured for carrier aggregation or dual connectivity mode). If theUE has only one serving cell that has high congestion (e.g., a high LBTfailure rate, a high CCA failure rate, and/or a high channel occupancy)or the UE's Peen is experiencing high congestion, the UE may not disableuplink transmissions on that because no communication to the gNB in theuplink may otherwise be possible.

In some embodiments, if a certain NR-U serving cell is experiencing highcongestion, a UE may not consider this congested unlicensed cell for anAUL transmission. In such embodiments, if AUL is enabled for anunlicensed cell that is experiencing high congestion, the UE may refrainfrom generating and transmitting a TB on that cell (e.g., the UE mayautonomously release the AUL grants configured for the congested NR-Ucell). It should be noted that for AUL transmissions, the UEautonomously decides to transmit a TB (e.g., upon arrival of uplink datain the buffer). In certain embodiments, if a UE keeps using an NR-U cellfor uplink transmissions irrespective of high congestion, the UE maygenerate TBs (e.g., for AUL transmissions) that may get stuck on thatcongested NR-U cell for transmission. This may in turn lead to anincreased reordering delay at the receiving side. It should be notedthat internally routing already generated TBs to a different servingcell may not work well (e.g., due to non-matching TB sizes and othercomplexities). As may be appreciated, in the first embodiment, a MAClayer may be aware of whether a serving cell is experiencing highcongestion. This may be ensured by UE internal communication (e.g., thePHY may report LBT and/or CCA failures or channel occupancy to the MACor may notify the MAC about predefined events like LBT and/or CCAfailures or channel occupancy exceeding a certain threshold).

In some embodiments, in addition to a buffer size, a UE may consider anLBT failure rate, a CCA failure rate, and/or a channel occupancy of anunlicensed cell if determining whether to perform an autonomous uplinktransmission. In certain embodiments, a UE performs an autonomous uplinktransmission unless there is no data available for transmission (e.g.,if no data is available the UE may skip the autonomous uplinktransmission). In certain embodiments of the first embodiment, the UEmay consider also an LBT failure rate, a CCA failure rate, and/orchannel occupancy in addition to a buffers status if determining whetherto perform an AUL transmission or whether to skip an AUL transmission.If an LBT failure rate, a CCA failure rate, or a channel occupancy istoo high (e.g., exceeding a preconfigured threshold), the UE may skip anAUL transmission even if there is data available for transmission.

In various implementations of the first embodiment, the UE may restrictcertain logical channels for transmission on an unlicensed cell that isexperiencing a high LBT failure rate, a high CCA failure rate, and/orhigh channel occupancy. In such implementations, only those logicalchannels that are delay intolerant (e.g., service may tolerate largetransmission and/or reordering delay), may be mapped to a NR-U cell forwhich channel access may fail for a longer time. In certain embodiments,an RRC configuration for each logical channel may indicate whether acorresponding logical channel may be mapped to an NR-U cell that isexperiencing high congestion. This may be done using a one bit flag. Insome embodiments, only logical channels and/or bearers configured with acertain 5QI value are allowed to be mapped to an NR-U cell experiencinghigh congestion.

In some implementations of the first embodiment, the UE may autonomouslysuspend AUL configurations configured for a cell that is experiencinghigh congestion/high LBT failures.

In various embodiments, a gNB may configure an LBT failure ratethreshold, a CCA failure rate threshold, and/or a channel occupancythreshold for an unlicensed cell. If the determined and/or measured CCAfailure rate, LBT failure rate, number of LBT failures, and/or channeloccupancy exceeds the threshold and/or is greater than or equal to thethreshold, the UE may autonomously stop and/or suspend UL transmissionson that cell or may not perform any autonomous uplink transmission.

In a second embodiment, a UE may take into account an LBT failure rate,a CCA failure rate, or a channel occupancy of an unlicensed cell ifdeciding on the routing of PDCP PDUs in a transmitting PDCP entity toassociated RLC entities for split bearer operation. In certainembodiments, routing is performed by PDCP for split bearers byconsidering a configured threshold, (e.g., ul-DataSplitThreshold). Ifthe total amount of PDCP data volume and RLC data volume pending forinitial transmission in the two associated RLC entities is equal to orlarger than ul-DataSplitThreshold, a PDCP transmitting entity submitsthe PDCP PDU to either the primary RLC entity or the secondary RLCentity, or else the PDCP PDUs are submitted to the primary RLC entity.

In various embodiments, such as in NR-U, an impact of LBT may beconsidered for routing data to the different paths (e.g., primary and/orsecondary RLC entity) for split bearer operation. This may be beneficialif one of the paths of the split bearer is over an unlicensed spectrumand the other path is over a licensed spectrum. If the channelconditions in the unlicensed spectrum changes (e.g., channel occupancyor probability of successful LBT and/or CCA drops to a low level, suchas below a preconfigured threshold), the UE may continue to transmit bysubmitting the PDCP PDU only to the licensed spectrum regardless of theconfigured threshold. Otherwise reordering delay may be increased ifdata is stuck on one link which cannot be used for transmission due tohigh congestion. In one implementation of the second embodiment, the UEonly considers serving cells for routing of PDCP PDUs in thetransmitting PDCP entity that are not highly congested. If all servingcells of a cell group are highly congested, a transmitting PDCP entitymay not submit PDCP PDUs to the RLC entity of the cell group. In someembodiments, a UE may temporarily deactivate and/or suspend a cell groupfor PDCP routing regardless of a configured threshold (e.g., even if atotal amount of PDCP data volume and RLC data volume pending for initialtransmission in the associated RLC entities is equal to or larger thanul-dataSplitThreshold). In certain embodiments, a UE may route PDCP PDUsto a cell group that is not deactivated and/or suspended for routing. Invarious embodiments, a UE may ignore a configured thresholdul-dataSplitThreshold and a configuration of a primary and/or secondaryRLC entity for routing operation.

In some embodiments, a UE uses legacy routing rules (e.g., based on aconfigured threshold ul-dataSplitThreshold and/or RLC configurations)for cell groups for which at least one serving cell is not congested forwhich at least one serving cell is active for routing.

In certain implementations of the second embodiment, the UE doesn'treport buffer status information for bearers of a cell group that istemporarily deactivated and/or suspended due to high congestion. Forexample, a PDCP transmitting entity doesn't indicate a PDCP data volumeto a MAC entity for the purpose of buffer status reporting associatedwith a cell group temporarily deactivated and/or suspended for routingpurposes (e.g., the PDCP data volume is set to zero). In someembodiments, a UE may set an RLC data volume to zero for bearers of acell group that is temporarily deactivated and/or suspended due to highcongestion.

In a third embodiment, a gNB configures a UE to indicate whether the UEis allowed to autonomously deactivate and/or suspend an unlicensedserving cell (e.g., temporarily deactivate the uplink of an unlicensedcell) if the serving cell is experiencing high congestion.

In one implementation of the third embodiment, the UE starts a timer ifthe serving cell is experiencing high congestion and deactivates and/orsuspends the serving cell (e.g., for the purpose of UL transmission andPDCP routing) as long as the timer is running. In such animplementation, the timer may be started in a MAC layer and the servingcell may be deactivated and/or suspended if the measured and/ordetermined LBT failure rate and/or CCA failure rate exceeds apreconfigured threshold or if PHY indicates to the MAC layer a high LBTfailure event, a high CCA failure event, a high channel occupancy,and/or another predefined case.

In certain implementations of the third embodiment, the UE autonomouslydeactivates and/or suspends an unlicensed serving cell (e.g.,temporarily deactivate the uplink of an unlicensed cell) for ULtransmission or PDCP routing as described in the first and secondembodiment if the serving cell is experiencing high congestion andactivates the serving cell (e.g., resumes the previously suspendeduplink operations) if the channel occupancy, LBT failure rate, and/orCCA failure rate gets back to a normal level of congestion (e.g., basedon an indication from PHY). High congestion and/or a normal level ofcongestion may be determined in a UE based on configured thresholds.

In various embodiments, a UE may inform a gNB if the UE has temporarilydeactivated and/or suspended an unlicensed cell due to high congestion.An indication used to inform the gNB may be made using physical controlsignaling, MAC control signaling, or any higher layer signaling. Thesignaling may be done via a serving cell (e.g., if the UE is aggregatingmultiple serving cells) that is not congested. In some embodiments, theindication may be transmitted on a congested unlicensed cell by a randomaccess procedure (e.g., using a predefined preamble and/or PRACHresource) that indicates the high congestion. Similar indications and/orsignaling may be used by the UE to inform the gNB that a NR-U cellpreviously experiencing high congestion has returned to a normal levelof congestion (e.g., a previously deactivated and/or suspendedunlicensed cell has been activated and/or resumed).

FIG. 4 is a flow chart diagram illustrating one embodiment of a method400 for autonomous bandwidth part switching. In some embodiments, themethod 400 is performed by an apparatus, such as the remote unit 102. Incertain embodiments, the method 400 may be performed by a processorexecuting program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 400 may include determining 402 that a channel parametercorresponding to an active uplink bandwidth part of a serving cell isgreater than a predetermined value at a time in which the active uplinkbandwidth part is a first bandwidth part. In some embodiments, themethod 400 includes, in response to determining that the channelparameter is greater than the predetermined value, autonomouslyswitching 404 the active uplink bandwidth part from the first uplinkbandwidth part to a second uplink bandwidth part configured for theserving cell, wherein switching the active uplink bandwidth partcomprises deactivating the first uplink bandwidth part.

In certain embodiments, the channel parameter comprises a measure oflisten before talk failures. In some embodiments, the predeterminedvalue is configured by a network entity. In various embodiments, themethod 400 further comprises performing a random access procedure inresponse to autonomously switching the active uplink bandwidth part.

In one embodiment, the method 400 further comprises receivinginformation enabling autonomous switching of the active uplink bandwidthpart. In certain embodiments, the method 400 further comprisesautonomously suspending configured uplink grants corresponding to theactive uplink bandwidth part of the serving cell in response todetermining that the channel parameter is greater than the predeterminedvalue. In some embodiments, autonomously suspending the configureduplink grants corresponding to the active uplink bandwidth part of theserving cell comprises suspending the configured uplink grantscorresponding to the active uplink bandwidth part without receivinginstructions from a network device indicating to suspend the configureduplink grants.

In various embodiments, deactivating the first uplink bandwidth partcomprises deactivating the first uplink bandwidth part without receivinginstructions from a network device indicating to deactivate the firstuplink bandwidth part. In one embodiment, the first uplink bandwidthpart and the second uplink bandwidth part correspond to an unlicensedcell. In certain embodiments, the method 400 further comprisestransmitting information indicating that the channel parametercorresponding to the active uplink bandwidth part of the serving cell isgreater than the predetermined value.

In some embodiments, the information is transmitted via a non-congestedserving cell. In various embodiments, the information is transmitted viaphysical control signaling, medium access control signaling, or highlayer signaling.

In one embodiment, a method comprises: determining that a channelparameter corresponding to an active uplink bandwidth part of a servingcell is greater than a predetermined value at a time in which the activeuplink bandwidth part is a first bandwidth part; and in response todetermining that the channel parameter is greater than the predeterminedvalue, autonomously switching the active uplink bandwidth part from thefirst uplink bandwidth part to a second uplink bandwidth part configuredfor the serving cell, wherein switching the active uplink bandwidth partcomprises deactivating the first uplink bandwidth part.

In certain embodiments, the channel parameter comprises a measure oflisten before talk failures.

In some embodiments, the predetermined value is configured by a networkentity.

In various embodiments, the method further comprises performing a randomaccess procedure in response to autonomously switching the active uplinkbandwidth part.

In one embodiment, the method further comprises receiving informationenabling autonomous switching of the active uplink bandwidth part.

In certain embodiments, the method further comprises autonomouslysuspending configured uplink grants corresponding to the active uplinkbandwidth part of the serving cell in response to determining that thechannel parameter is greater than the predetermined value.

In some embodiments, autonomously suspending the configured uplinkgrants corresponding to the active uplink bandwidth part of the servingcell comprises suspending the configured uplink grants corresponding tothe active uplink bandwidth part without receiving instructions from anetwork device indicating to suspend the configured uplink grants.

In various embodiments, deactivating the first uplink bandwidth partcomprises deactivating the first uplink bandwidth part without receivinginstructions from a network device indicating to deactivate the firstuplink bandwidth part.

In one embodiment, the first uplink bandwidth part and the second uplinkbandwidth part correspond to an unlicensed cell.

In certain embodiments, the method further comprises transmittinginformation indicating that the channel parameter corresponding to theactive uplink bandwidth part of the serving cell is greater than thepredetermined value.

In some embodiments, the information is transmitted via a non-congestedserving cell.

In various embodiments, the information is transmitted via physicalcontrol signaling, medium access control signaling, or high layersignaling.

In one embodiment, an apparatus comprises: a processor that: determinesthat a channel parameter corresponding to an active uplink bandwidthpart of a serving cell is greater than a predetermined value at a timein which the active uplink bandwidth part is a first bandwidth part;and, in response to determining that the channel parameter is greaterthan the predetermined value, autonomously switches the active uplinkbandwidth part from the first uplink bandwidth part to a second uplinkbandwidth part configured for the serving cell, wherein switching theactive uplink bandwidth part comprises deactivating the first uplinkbandwidth part.

In certain embodiments, the channel parameter comprises a measure oflisten before talk failures.

In some embodiments, the predetermined value is configured by a networkentity.

In various embodiments, the processor performs a random access procedurein response to autonomously switching the active uplink bandwidth part.

In one embodiment, the apparatus further comprises a receiver thatreceives information enabling autonomous switching of the active uplinkbandwidth part.

In certain embodiments, the processor autonomously suspends configureduplink grants corresponding to the active uplink bandwidth part of theserving cell in response to determining that the channel parameter isgreater than the predetermined value.

In some embodiments, the processor autonomously suspending theconfigured uplink grants corresponding to the active uplink bandwidthpart of the serving cell comprises the processor suspending theconfigured uplink grants corresponding to the active uplink bandwidthpart without receiving instructions from a network device indicating tosuspend the configured uplink grants.

In various embodiments, deactivating the first uplink bandwidth partcomprises deactivating the first uplink bandwidth part without receivinginstructions from a network device indicating to deactivate the firstuplink bandwidth part.

In one embodiment, the first uplink bandwidth part and the second uplinkbandwidth part correspond to an unlicensed cell.

In certain embodiments, the apparatus further comprises a transmitterthat transmits information indicating that the channel parametercorresponding to the active uplink bandwidth part of the serving cell isgreater than the predetermined value.

In some embodiments, the information is transmitted via a non-congestedserving cell.

In various embodiments, the information is transmitted via physicalcontrol signaling, medium access control signaling, or high layersignaling.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

The invention claimed is:
 1. An apparatus comprising: a processor; and amemory coupled to the processor, the memory comprising instructionsexecutable by the processor to cause the processor to: determine that achannel access parameter associated with to an active uplink bandwidthpart (BWP) of a serving cell satisfies a threshold value, wherein theactive uplink BWP comprises a first uplink BWP, and wherein the servingcell comprises an unlicensed cell; switch, in response to the channelaccess parameter satisfying the threshold value, from the first uplinkBWP to a second uplink BWP configured for the serving cell; suspend aconfigured uplink grant associated with the first uplink BWP; andperform a random access procedure on the unlicensed cell for the seconduplink BWP.
 2. The apparatus of claim 1, wherein the instructions arefurther executable by the processor to cause the apparatus to receiveinformation enabling the apparatus to autonomously switch from the firstuplink BWP to the second uplink BWP.
 3. The apparatus of claim 1,wherein the instructions to suspend the configured uplink grant arefurther executable by the processor to cause the apparatus toautonomously suspend the configured uplink grant in response to thechannel parameter satisfying the threshold value.
 4. The apparatus ofclaim 3, wherein the instructions to autonomously suspend the configureduplink grant are further executable by the processor to cause theapparatus to suspend the configured uplink grant irrespective of acommand from a network device.
 5. The apparatus of claim 1, wherein theinstructions are further executable by the processor to cause theapparatus to deactivate the first uplink BWP irrespective of a commandfrom a network device.
 6. The apparatus of claim 1, wherein theinstructions are further executable by the processor to cause theapparatus to transmit an indication indicating that the channelparameter satisfies the threshold value.
 7. The apparatus of claim 6,wherein the indication is transmitted via a non-congested serving cell.8. The apparatus of claim 6, wherein the indication is transmitted viaphysical control signaling, medium access control signaling, or highlayer signaling.
 9. A method comprising: determining that a channelaccess parameter associated with to an active uplink bandwidth part(BWP) of a serving cell satisfies a threshold value, wherein the activeuplink BWP comprises a first uplink BWP, and wherein the serving cellcomprises an unlicensed cell; switching, in response to the channelaccess parameter satisfying the threshold value, from the first uplinkBWP bandwidth part to a second uplink BWP configured for the servingcell; suspending a configured uplink grant associated with the firstuplink BWP; and performing a random access procedure on the unlicensedcell for the second uplink BWP.
 10. The method of claim 9, wherein thechannel access parameter comprises a measure of listen before talk (LBT)failures.
 11. The method of claim 9, wherein the channel accessparameter comprises a counter counting LBT failures indicated by lowerlayers.
 12. The method of claim 9, wherein the threshold value isconfigured by a network entity.
 13. The method of claim 9, furthercomprising receiving an indication enabling switching of the activeuplink BWP.
 14. The method of claim 9, further comprising suspending theconfigured uplink grant in response to that the channel parametersatisfying the threshold value.
 15. The method of claim 14, whereinsuspending the configured uplink grant comprises suspending theconfigured uplink grant irrespective of a command from a network device.16. The method of claim 9, wherein deactivating the first uplink BWPcomprises deactivating the first uplink BWP irrespective of a commandfrom a network device.
 17. The method of claim 9, wherein the firstuplink BWP and the second uplink BWP correspond to an unlicensed cell.18. The method of claim 9, further comprising transmitting an indicationindicating that the channel parameter satisfies the threshold value. 19.The method of claim 18, wherein the indication is transmitted via anon-congested serving cell.
 20. The method of claim 18, wherein theindication is transmitted via physical control signaling, medium accesscontrol signaling, or high layer signaling.